Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbf6ea0a9be72fa82315b6ed8df6a1c67e9175a91c65f87fa64a1999b27b6fca

Tx prefix hash: 79f43a623b42b8778bc3b050dead7856c3d477ec37bd3ff020aec7b4d0230e8b
Tx public key: d1af25517de76027d39f7ad5b354cb2aa855e0de906861085226c0f44c8c5d56
Timestamp: 1763085741 Timestamp [UCT]: 2025-11-14 02:02:21 Age [y:d:h:m:s]: 00:039:15:34:38
Block: 1411637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28374 RingCT/type: yes/0
Extra: 01d1af25517de76027d39f7ad5b354cb2aa855e0de906861085226c0f44c8c5d560211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4c266f349f8079f552c9c99a495244986db1923a74364b475ab0294dcf34d5 0.600000000000 1900100 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": 1411647, "vin": [ { "gen": { "height": 1411637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4c266f349f8079f552c9c99a495244986db1923a74364b475ab0294dcf34d5" } } ], "extra": [ 1, 209, 175, 37, 81, 125, 231, 96, 39, 211, 159, 122, 213, 179, 84, 203, 42, 168, 85, 224, 222, 144, 104, 97, 8, 82, 38, 192, 244, 76, 140, 93, 86, 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