Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deee6c44ec455e416502f46544c6fd785a8d0a860f913b9f64320dd46a09bced

Tx prefix hash: 6a35e527da776476f8dec56caaac7232e75db7bee808be717b21496f1edb01bf
Tx public key: 639287fd62d05becc02f8f3f25df8f14e98115a6d2e2160afd5ccde0d6d8c7f2
Timestamp: 1736797224 Timestamp [UCT]: 2025-01-13 19:40:24 Age [y:d:h:m:s]: 00:156:03:57:27
Block: 1196670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111304 RingCT/type: yes/0
Extra: 01639287fd62d05becc02f8f3f25df8f14e98115a6d2e2160afd5ccde0d6d8c7f2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a53a34b181fc136fc667cd27fcd85cc86a63fe36bded3cf42a8d406ec4e6bf04 0.600000000000 1683271 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": 1196680, "vin": [ { "gen": { "height": 1196670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a53a34b181fc136fc667cd27fcd85cc86a63fe36bded3cf42a8d406ec4e6bf04" } } ], "extra": [ 1, 99, 146, 135, 253, 98, 208, 91, 236, 192, 47, 143, 63, 37, 223, 143, 20, 233, 129, 21, 166, 210, 226, 22, 10, 253, 92, 205, 224, 214, 216, 199, 242, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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