Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f29f6ada2eda660df8c61f1c37b319ae5b4cbe11e6931ab6731266b9b5d08b

Tx prefix hash: 863d62a49a7c22d9850ff28f802757f5bdb3863060858cf2240ea9a43941910e
Tx public key: ab4fe8413e4cf4f3acc909aa3cb8bd86c6649a10084bf80b6927308c6948ad3a
Timestamp: 1737454017 Timestamp [UCT]: 2025-01-21 10:06:57 Age [y:d:h:m:s]: 00:334:22:26:09
Block: 1202065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236965 RingCT/type: yes/0
Extra: 01ab4fe8413e4cf4f3acc909aa3cb8bd86c6649a10084bf80b6927308c6948ad3a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 251f87d0a2f8425065dce5632fd60643e60a7071ebc0a4670adda232057e42f6 0.600000000000 1688724 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": 1202075, "vin": [ { "gen": { "height": 1202065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "251f87d0a2f8425065dce5632fd60643e60a7071ebc0a4670adda232057e42f6" } } ], "extra": [ 1, 171, 79, 232, 65, 62, 76, 244, 243, 172, 201, 9, 170, 60, 184, 189, 134, 198, 100, 154, 16, 8, 75, 248, 11, 105, 39, 48, 140, 105, 72, 173, 58, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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