Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db58c831a48023e57557669ed7e7ca0b0a5da9d9b7b9f6be220961fb22e300aa

Tx prefix hash: 8ba2ca9c646f976b35e9ed19b48bc908b335a43aeb48085c24160d3c171cd8d6
Tx public key: 81a6c123a704d5373f25a1035e124ebe9c5aa62f5467f6fbfc642d4a41dc1ce1
Timestamp: 1752888983 Timestamp [UCT]: 2025-07-19 01:36:23 Age [y:d:h:m:s]: 00:125:13:06:24
Block: 1328503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88511 RingCT/type: yes/0
Extra: 0181a6c123a704d5373f25a1035e124ebe9c5aa62f5467f6fbfc642d4a41dc1ce1021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b8430b35b81a1679e514ee3f1f76f50a36e10f380a1d3cb95f8b8343f4907b2 0.600000000000 1816266 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": 1328513, "vin": [ { "gen": { "height": 1328503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b8430b35b81a1679e514ee3f1f76f50a36e10f380a1d3cb95f8b8343f4907b2" } } ], "extra": [ 1, 129, 166, 193, 35, 167, 4, 213, 55, 63, 37, 161, 3, 94, 18, 78, 190, 156, 90, 166, 47, 84, 103, 246, 251, 252, 100, 45, 74, 65, 220, 28, 225, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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