Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9d75969747b04842f2051ec291712f6cdb7a7794bdb9acf77f8846669bf181b

Tx prefix hash: 7e89f4e721d6363ac8b02c96800bb188ba9ae22e197b302a4707ea8ec0e7828a
Tx public key: a3829fbcba55199dbcf4a0f5bed40d69d7b3e9c1a3f28407c84a0672a08c22d1
Timestamp: 1761914501 Timestamp [UCT]: 2025-10-31 12:41:41 Age [y:d:h:m:s]: 00:093:00:07:40
Block: 1401936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66398 RingCT/type: yes/0
Extra: 01a3829fbcba55199dbcf4a0f5bed40d69d7b3e9c1a3f28407c84a0672a08c22d102110000000c25a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df4b13131a791ca494cfa83f6f6a0134a34e4dd9af6f5a96204dde734ff3262d 0.600000000000 1890255 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": 1401946, "vin": [ { "gen": { "height": 1401936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df4b13131a791ca494cfa83f6f6a0134a34e4dd9af6f5a96204dde734ff3262d" } } ], "extra": [ 1, 163, 130, 159, 188, 186, 85, 25, 157, 188, 244, 160, 245, 190, 212, 13, 105, 215, 179, 233, 193, 163, 242, 132, 7, 200, 74, 6, 114, 160, 140, 34, 209, 2, 17, 0, 0, 0, 12, 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