Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e65132313e4d80dda5d6569777f8cb9d1f16ad3d092cf2ab9305359f2e6d3df

Tx prefix hash: 7c7359eb13f0e7d74c583112b27b62d2e0d10fd25b014e25d4c45f3453c0344f
Tx public key: fdf8d78e20c9e9c33be0639d8d9e46fa81d2cd8ef9e62b6c16c5eb4d53540438
Timestamp: 1730333963 Timestamp [UCT]: 2024-10-31 00:19:23 Age [y:d:h:m:s]: 00:180:02:22:46
Block: 1143142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128586 RingCT/type: yes/0
Extra: 01fdf8d78e20c9e9c33be0639d8d9e46fa81d2cd8ef9e62b6c16c5eb4d535404380211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 567ba040c6af515da7388abb368ad957f52c00884e27476980bd61fbdf7cbcce 0.600000000000 1627005 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": 1143152, "vin": [ { "gen": { "height": 1143142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "567ba040c6af515da7388abb368ad957f52c00884e27476980bd61fbdf7cbcce" } } ], "extra": [ 1, 253, 248, 215, 142, 32, 201, 233, 195, 59, 224, 99, 157, 141, 158, 70, 250, 129, 210, 205, 142, 249, 230, 43, 108, 22, 197, 235, 77, 83, 84, 4, 56, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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