Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3cb10a279d26a329921d79244086a2160f0b64d8b208b04602d127439def532

Tx prefix hash: 708b8db58c0ab3677c06be2277b3dff77fec070e8a5faa9b974777cc8dd3e8f0
Tx public key: 3f425f6dcb918c320f22a48ad8f99fa3dd7aef0fe54e961a69406e64036837c2
Timestamp: 1704591441 Timestamp [UCT]: 2024-01-07 01:37:21 Age [y:d:h:m:s]: 01:330:10:40:18
Block: 929785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495045 RingCT/type: yes/0
Extra: 013f425f6dcb918c320f22a48ad8f99fa3dd7aef0fe54e961a69406e64036837c202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc54d7743081a1a0161256105e08d7326337024e560b91a04f5bcd4bd6f6fd03 0.600000000000 1387661 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": 929795, "vin": [ { "gen": { "height": 929785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc54d7743081a1a0161256105e08d7326337024e560b91a04f5bcd4bd6f6fd03" } } ], "extra": [ 1, 63, 66, 95, 109, 203, 145, 140, 50, 15, 34, 164, 138, 216, 249, 159, 163, 221, 122, 239, 15, 229, 78, 150, 26, 105, 64, 110, 100, 3, 104, 55, 194, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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