Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd16169b21717f08817aa6637f3fc2b84f40254fa2763d443ebd193b18701da

Tx prefix hash: 533b96c076f475b0b0cef3d9e6eb8a7ccbd54a1e59269c8ce790778280ec7aab
Tx public key: d99e17b4c1eb375984fad704dda1fc3625f3a630ba69c29a4d539895d335fafd
Timestamp: 1706409309 Timestamp [UCT]: 2024-01-28 02:35:09 Age [y:d:h:m:s]: 01:028:08:49:21
Block: 944857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281328 RingCT/type: yes/0
Extra: 01d99e17b4c1eb375984fad704dda1fc3625f3a630ba69c29a4d539895d335fafd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e0c2dbb78bb1a1531424d3c98da9e303053385bb55cd39342b2e8f465e3dcb9 0.600000000000 1403147 of 15

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": 944867, "vin": [ { "gen": { "height": 944857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e0c2dbb78bb1a1531424d3c98da9e303053385bb55cd39342b2e8f465e3dcb9" } } ], "extra": [ 1, 217, 158, 23, 180, 193, 235, 55, 89, 132, 250, 215, 4, 221, 161, 252, 54, 37, 243, 166, 48, 186, 105, 194, 154, 77, 83, 152, 149, 211, 53, 250, 253, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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