Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f51566704e8579a6981e63814ace2af2f1a8cc21d2ea4f2baa5c7f02fb49b8a

Tx prefix hash: bcd3e19a34be94c5d40d4ac72b2ed4c9d5bc4a7152ce5b76608defeefbaf4262
Tx public key: 029c4a8819638088c04430e789c3f4dbb765f9282a6f22a7f3089ba11fa2c900
Timestamp: 1746524635 Timestamp [UCT]: 2025-05-06 09:43:55 Age [y:d:h:m:s]: 00:198:22:41:04
Block: 1276928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139893 RingCT/type: yes/0
Extra: 01029c4a8819638088c04430e789c3f4dbb765f9282a6f22a7f3089ba11fa2c90002110000000b9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 061732c4e14ec783c320e8d8fd33f796268cd13795fe35ecef83e6e1b0d08770 0.600000000000 1764279 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": 1276938, "vin": [ { "gen": { "height": 1276928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "061732c4e14ec783c320e8d8fd33f796268cd13795fe35ecef83e6e1b0d08770" } } ], "extra": [ 1, 2, 156, 74, 136, 25, 99, 128, 136, 192, 68, 48, 231, 137, 195, 244, 219, 183, 101, 249, 40, 42, 111, 34, 167, 243, 8, 155, 161, 31, 162, 201, 0, 2, 17, 0, 0, 0, 11, 159, 159, 230, 140, 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