Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3b3135f721852f136cb85a5adff8b96d672728b3113069bcede3832b4289d3

Tx prefix hash: f4fa319025e3d2449d424aa1a16f8387c0e41b187853c60250a262f31a7ba9f5
Tx public key: 6d077f1d30a4a53b3dd2411db1a7398dcd9645b0f41283ab125fcf34d05ca106
Timestamp: 1762135927 Timestamp [UCT]: 2025-11-03 02:12:07 Age [y:d:h:m:s]: 00:017:23:25:25
Block: 1403749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12869 RingCT/type: yes/0
Extra: 016d077f1d30a4a53b3dd2411db1a7398dcd9645b0f41283ab125fcf34d05ca10602110000000a5dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6724d9f10a27e351304caea3f41cd5d32555cbc545c0d882d8738cf1403e463 0.600000000000 1892102 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": 1403759, "vin": [ { "gen": { "height": 1403749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6724d9f10a27e351304caea3f41cd5d32555cbc545c0d882d8738cf1403e463" } } ], "extra": [ 1, 109, 7, 127, 29, 48, 164, 165, 59, 61, 210, 65, 29, 177, 167, 57, 141, 205, 150, 69, 176, 244, 18, 131, 171, 18, 95, 207, 52, 208, 92, 161, 6, 2, 17, 0, 0, 0, 10, 93, 251, 190, 42, 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