Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966328d357524e02588dd0ea3929ba0504a157ac0d72c49c2c57e1f7ced7bedf

Tx prefix hash: ef75bc6c54eea11d26f7225784fcc43dc3aa56e0fc7b6a8a6290720d373343c6
Tx public key: 357e8dc9a6d346ec1dc6253686cf755733830cf6f3441d4767b037cf508b6efb
Timestamp: 1640865807 Timestamp [UCT]: 2021-12-30 12:03:27 Age [y:d:h:m:s]: 03:075:12:48:55
Block: 406736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832755 RingCT/type: yes/0
Extra: 01357e8dc9a6d346ec1dc6253686cf755733830cf6f3441d4767b037cf508b6efb02110000003eed5d3ead000000000000000000

1 output(s) for total of 27.562279308000 dcy

stealth address amount amount idx
00: 9d0fa92ce343646492d481ec9e70b501000af3547511f18c219343fa6cf337f6 27.562279308000 807802 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": 406746, "vin": [ { "gen": { "height": 406736 } } ], "vout": [ { "amount": 27562279308, "target": { "key": "9d0fa92ce343646492d481ec9e70b501000af3547511f18c219343fa6cf337f6" } } ], "extra": [ 1, 53, 126, 141, 201, 166, 211, 70, 236, 29, 198, 37, 54, 134, 207, 117, 87, 51, 131, 12, 246, 243, 68, 29, 71, 103, 176, 55, 207, 80, 139, 110, 251, 2, 17, 0, 0, 0, 62, 237, 93, 62, 173, 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