Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 000d64e6634cce43258f4360ba740f02f1bbcfdf537b42d9905ab46b1c1e11f5

Tx prefix hash: 226546819b37daab0ef8f0ec1f81782fff3c0e041e551f936f59d91a9d1982e1
Tx public key: 0f79230aeac0fc2922baf744884c4b8d2c42e250c0cbcba6e7fc8b61f5861033
Timestamp: 1719338831 Timestamp [UCT]: 2024-06-25 18:07:11 Age [y:d:h:m:s]: 00:351:17:59:11
Block: 1052060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251374 RingCT/type: yes/0
Extra: 010f79230aeac0fc2922baf744884c4b8d2c42e250c0cbcba6e7fc8b61f586103302110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a3f8bfcd9454e5ef6cf76503f5a0d52c2c1665aa4f1919978cc4125a2a25c93 0.600000000000 1522381 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": 1052070, "vin": [ { "gen": { "height": 1052060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a3f8bfcd9454e5ef6cf76503f5a0d52c2c1665aa4f1919978cc4125a2a25c93" } } ], "extra": [ 1, 15, 121, 35, 10, 234, 192, 252, 41, 34, 186, 247, 68, 136, 76, 75, 141, 44, 66, 226, 80, 192, 203, 203, 166, 231, 252, 139, 97, 245, 134, 16, 51, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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