Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa58c5b3f36dd5f4a5562c8758388d904595bdac2f3f979cf02fa729c5fcf65d

Tx prefix hash: 63404de3ccabb4b9588e651ca31aab80b5d7eb9a6b8eeecb28e1bcb7e22708b3
Tx public key: 062aea035a646c1c2f78e9b057393e518f07091eece47bccf6328c9335b8b066
Timestamp: 1760602759 Timestamp [UCT]: 2025-10-16 08:19:19 Age [y:d:h:m:s]: 00:081:10:32:56
Block: 1391057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58331 RingCT/type: yes/0
Extra: 01062aea035a646c1c2f78e9b057393e518f07091eece47bccf6328c9335b8b0660211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d958b9c2b2a264d4bead23ef726ff85c78cce7724a493917965cc84676e5600 0.600000000000 1879304 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": 1391067, "vin": [ { "gen": { "height": 1391057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d958b9c2b2a264d4bead23ef726ff85c78cce7724a493917965cc84676e5600" } } ], "extra": [ 1, 6, 42, 234, 3, 90, 100, 108, 28, 47, 120, 233, 176, 87, 57, 62, 81, 143, 7, 9, 30, 236, 228, 123, 204, 246, 50, 140, 147, 53, 184, 176, 102, 2, 17, 0, 0, 0, 3, 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