Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3684b22931b2f1db9a9bdd3666086ca97fa4eb783e8d053a072598b090a56ff

Tx prefix hash: dd2ea8336969867d2e333c559303c98d662428555e1f6996a22f8ecfb9f33323
Tx public key: da1e0afef57e62436d7203b3d92ff1c980d824f2f67c30077ef1309b09c8b3ee
Timestamp: 1682828492 Timestamp [UCT]: 2023-04-30 04:21:32 Age [y:d:h:m:s]: 01:300:12:24:37
Block: 749637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475987 RingCT/type: yes/0
Extra: 01da1e0afef57e62436d7203b3d92ff1c980d824f2f67c30077ef1309b09c8b3ee02110000000175e3f0e9000000000000000000

1 output(s) for total of 2.014381079000 dcy

stealth address amount amount idx
00: 06a791ed2814c7835a0c2f3cca70ebc28cbf3244e886b03f9634b1ec16dbb14a 2.014381079000 1197626 of 0

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": 749647, "vin": [ { "gen": { "height": 749637 } } ], "vout": [ { "amount": 2014381079, "target": { "key": "06a791ed2814c7835a0c2f3cca70ebc28cbf3244e886b03f9634b1ec16dbb14a" } } ], "extra": [ 1, 218, 30, 10, 254, 245, 126, 98, 67, 109, 114, 3, 179, 217, 47, 241, 201, 128, 216, 36, 242, 246, 124, 48, 7, 126, 241, 48, 155, 9, 200, 179, 238, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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