Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 24134d2e067b57833febaa6a691791613a4b0390017a01ec5449f1584dd9dc44

Tx prefix hash: 349ec2e195c6018819ae68127bdbe8086a56e0f71724dec2a2720f7c1713a8f9
Tx public key: 0dea7b28df89d0f103c70887d913813ad78b91ef40aadf902da2c1d59acbd440
Timestamp: 1578656352 Timestamp [UCT]: 2020-01-10 11:39:12 Age [y:d:h:m:s]: 05:098:06:05:10
Block: 42600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220260 RingCT/type: yes/0
Extra: 010dea7b28df89d0f103c70887d913813ad78b91ef40aadf902da2c1d59acbd44002110000000e17786bcf000000000000000000

1 output(s) for total of 443.454799608000 dcy

stealth address amount amount idx
00: 8d1c787cfd6dd2eb0947e85d85b5603b14e080e1af935b9e713fc440b3d980b8 443.454799608000 76804 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 42610, "vin": [ { "gen": { "height": 42600 } } ], "vout": [ { "amount": 443454799608, "target": { "key": "8d1c787cfd6dd2eb0947e85d85b5603b14e080e1af935b9e713fc440b3d980b8" } } ], "extra": [ 1, 13, 234, 123, 40, 223, 137, 208, 241, 3, 199, 8, 135, 217, 19, 129, 58, 215, 139, 145, 239, 64, 170, 223, 144, 45, 162, 193, 213, 154, 203, 212, 64, 2, 17, 0, 0, 0, 14, 23, 120, 107, 207, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8