Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cad9cba22e92b6cb9187a8eef8e10533205fb8fae63e66062e3974d914fdf26

Tx prefix hash: 99a1df6f5529909e85ae07673c29cecc7b6540b8f9ffa929f3775fd3bab40a66
Tx public key: 64c8c8dc66663ad72a0db866ea8f189c6c69c03e86d01662e10807761347924f
Timestamp: 1739633215 Timestamp [UCT]: 2025-02-15 15:26:55 Age [y:d:h:m:s]: 00:278:08:58:25
Block: 1219848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196734 RingCT/type: yes/0
Extra: 0164c8c8dc66663ad72a0db866ea8f189c6c69c03e86d01662e10807761347924f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bf9cf05417838e9aa8c6a0dfb84dc9d4268abe3e8525b1c707a0d505405a197 0.600000000000 1706681 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": 1219858, "vin": [ { "gen": { "height": 1219848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bf9cf05417838e9aa8c6a0dfb84dc9d4268abe3e8525b1c707a0d505405a197" } } ], "extra": [ 1, 100, 200, 200, 220, 102, 102, 58, 215, 42, 13, 184, 102, 234, 143, 24, 156, 108, 105, 192, 62, 134, 208, 22, 98, 225, 8, 7, 118, 19, 71, 146, 79, 2, 17, 0, 0, 0, 4, 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