Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e81c21c41fdc1b44a6c56ecf85f8dcb1cf223d27af9e72125828929e39435b

Tx prefix hash: 446712272d9307bc694c0da18c520b41dde1ddc635de85a6d4b3940597f03a5f
Tx public key: 76514a11bc81480ba2a9c7d62071054ad5066d617138f286ecbc95c6c80b76cb
Timestamp: 1583754110 Timestamp [UCT]: 2020-03-09 11:41:50 Age [y:d:h:m:s]: 05:240:20:02:45
Block: 79490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1325156 RingCT/type: yes/0
Extra: 0176514a11bc81480ba2a9c7d62071054ad5066d617138f286ecbc95c6c80b76cb02110000000228db8c57000000000000000000

1 output(s) for total of 334.670492506000 dcy

stealth address amount amount idx
00: cabf941aee4b656a5809762d3a09dc2a3b656f57b07e28542d3319d0419d6323 334.670492506000 145352 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": 79500, "vin": [ { "gen": { "height": 79490 } } ], "vout": [ { "amount": 334670492506, "target": { "key": "cabf941aee4b656a5809762d3a09dc2a3b656f57b07e28542d3319d0419d6323" } } ], "extra": [ 1, 118, 81, 74, 17, 188, 129, 72, 11, 162, 169, 199, 214, 32, 113, 5, 74, 213, 6, 109, 97, 113, 56, 242, 134, 236, 188, 149, 198, 200, 11, 118, 203, 2, 17, 0, 0, 0, 2, 40, 219, 140, 87, 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