Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb8868dc1beabbc51879dcddb3f9aecd1ef749d8eac0256d26fbb0be0c280290

Tx prefix hash: d095e31fd0f7f2534ed09c680847d64b4a355f7f1e8bccec9465faa9259e01ab
Tx public key: b1ef8ad2fbedefc308700d6e318bb02a7afd086fe1edc3e8078d72ed64125b2f
Timestamp: 1735623471 Timestamp [UCT]: 2024-12-31 05:37:51 Age [y:d:h:m:s]: 00:171:18:30:01
Block: 1186950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122435 RingCT/type: yes/0
Extra: 01b1ef8ad2fbedefc308700d6e318bb02a7afd086fe1edc3e8078d72ed64125b2f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33f8aa981ada0be25f148e464426db7bb97f496d73c32a01bd75c826f316ea17 0.600000000000 1673435 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": 1186960, "vin": [ { "gen": { "height": 1186950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33f8aa981ada0be25f148e464426db7bb97f496d73c32a01bd75c826f316ea17" } } ], "extra": [ 1, 177, 239, 138, 210, 251, 237, 239, 195, 8, 112, 13, 110, 49, 139, 176, 42, 122, 253, 8, 111, 225, 237, 195, 232, 7, 141, 114, 237, 100, 18, 91, 47, 2, 17, 0, 0, 0, 1, 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