Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbbcf94ad19fc9a303d279fecb167219c3e9a4c446dececd349642ea63029cf1

Tx prefix hash: ad41b5884107b8c91712b095813495a78f21c2c75e041f948512d7d83e01ace9
Tx public key: e7af4ffb9a563f8a2a18b4e8a9a691234f3b1a00aea2154cb3b0b363769fd24e
Timestamp: 1737032419 Timestamp [UCT]: 2025-01-16 13:00:19 Age [y:d:h:m:s]: 00:153:23:22:13
Block: 1198616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109727 RingCT/type: yes/0
Extra: 01e7af4ffb9a563f8a2a18b4e8a9a691234f3b1a00aea2154cb3b0b363769fd24e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b37036968cee709042ef24e70bb2edd879f2e1a6b4cbef61c941f9303c24763b 0.600000000000 1685241 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": 1198626, "vin": [ { "gen": { "height": 1198616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b37036968cee709042ef24e70bb2edd879f2e1a6b4cbef61c941f9303c24763b" } } ], "extra": [ 1, 231, 175, 79, 251, 154, 86, 63, 138, 42, 24, 180, 232, 169, 166, 145, 35, 79, 59, 26, 0, 174, 162, 21, 76, 179, 176, 179, 99, 118, 159, 210, 78, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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