Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef182f3fded25a4443596f4fdab4c31f8e95a0001461a971524f16ecc67b151

Tx prefix hash: 5f84607f17d463fe569728c0ad1f89237a84c8c10a4d47a1f8a2e672e9e97b83
Tx public key: 24e3cbf0e0e76d2dc1f2b5fc13ea9ce7040b725b66651806af4e2cacbbf88631
Timestamp: 1762255019 Timestamp [UCT]: 2025-11-04 11:16:59 Age [y:d:h:m:s]: 00:015:20:44:30
Block: 1404749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11356 RingCT/type: yes/0
Extra: 0124e3cbf0e0e76d2dc1f2b5fc13ea9ce7040b725b66651806af4e2cacbbf8863102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eb0d03be0af93d4ea55718b99d34a9dc68f1a4cfc2b8428fb9b9a40f6af32b4 0.600000000000 1893108 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": 1404759, "vin": [ { "gen": { "height": 1404749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eb0d03be0af93d4ea55718b99d34a9dc68f1a4cfc2b8428fb9b9a40f6af32b4" } } ], "extra": [ 1, 36, 227, 203, 240, 224, 231, 109, 45, 193, 242, 181, 252, 19, 234, 156, 231, 4, 11, 114, 91, 102, 101, 24, 6, 175, 78, 44, 172, 187, 248, 134, 49, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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