Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441700bd4084c5e5796e4bd2a1dabf58a71445f263b31543f5f168cc0e4a7d1a

Tx prefix hash: e35386f334fdee4167071a72b586e44a150f87ecd7087b7939139c706fbe42a2
Tx public key: cc9aec499b32750b43bd0f0f8b1ce7abfa8e8ad3de78bef1b03461e68b29c565
Timestamp: 1716637222 Timestamp [UCT]: 2024-05-25 11:40:22 Age [y:d:h:m:s]: 00:314:03:10:07
Block: 1029686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224514 RingCT/type: yes/0
Extra: 01cc9aec499b32750b43bd0f0f8b1ce7abfa8e8ad3de78bef1b03461e68b29c5650211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18e41af01a3cfca2d152b56a574fcc5459f4f7dca364f03c4be78d5522cd8a45 0.600000000000 1497843 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": 1029696, "vin": [ { "gen": { "height": 1029686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18e41af01a3cfca2d152b56a574fcc5459f4f7dca364f03c4be78d5522cd8a45" } } ], "extra": [ 1, 204, 154, 236, 73, 155, 50, 117, 11, 67, 189, 15, 15, 139, 28, 231, 171, 250, 142, 138, 211, 222, 120, 190, 241, 176, 52, 97, 230, 139, 41, 197, 101, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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