Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36d6f2c3a06e10b68b8388a34a412c2af323d417a89611663323cab6d189bff

Tx prefix hash: 3c2526f3e061e2a507efe0ecb58c4433ec5820c2d530ebac86069dcbb78365bb
Tx public key: ed817a1d2642146e1a5fc666496964fbada0ab2258d186bcd99a584b0edfe9c9
Timestamp: 1751183805 Timestamp [UCT]: 2025-06-29 07:56:45 Age [y:d:h:m:s]: 00:145:08:59:30
Block: 1315064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102015 RingCT/type: yes/0
Extra: 01ed817a1d2642146e1a5fc666496964fbada0ab2258d186bcd99a584b0edfe9c902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05ae358532fe3b145e97b2fccd58753d881dc68df6208c85377a621e36f6091d 0.600000000000 1802717 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": 1315074, "vin": [ { "gen": { "height": 1315064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05ae358532fe3b145e97b2fccd58753d881dc68df6208c85377a621e36f6091d" } } ], "extra": [ 1, 237, 129, 122, 29, 38, 66, 20, 110, 26, 95, 198, 102, 73, 105, 100, 251, 173, 160, 171, 34, 88, 209, 134, 188, 217, 154, 88, 75, 14, 223, 233, 201, 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