Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc24c9e5e42b69f316f478fd177f1539e5d9d9910f5e12edfd7443420a0c06cd

Tx prefix hash: 23a75ab947c0ba14a6058c16cf82e45a11e856d8086ab21ffa85b6677be896b8
Tx public key: 7370c7381d74fd248ac7980e449dc49966bc9fcd2e50be04304a24b74c50c820
Timestamp: 1639510999 Timestamp [UCT]: 2021-12-14 19:43:19 Age [y:d:h:m:s]: 03:022:09:33:43
Block: 395555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 794974 RingCT/type: yes/0
Extra: 017370c7381d74fd248ac7980e449dc49966bc9fcd2e50be04304a24b74c50c82002110000001fe60c8f99000000000000000000

1 output(s) for total of 30.018365133000 dcy

stealth address amount amount idx
00: 34528b76c4cfa8fbf21752c2a388547ac9a3ff8c00407e7d65e60ab819a8f887 30.018365133000 793516 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": 395565, "vin": [ { "gen": { "height": 395555 } } ], "vout": [ { "amount": 30018365133, "target": { "key": "34528b76c4cfa8fbf21752c2a388547ac9a3ff8c00407e7d65e60ab819a8f887" } } ], "extra": [ 1, 115, 112, 199, 56, 29, 116, 253, 36, 138, 199, 152, 14, 68, 157, 196, 153, 102, 188, 159, 205, 46, 80, 190, 4, 48, 74, 36, 183, 76, 80, 200, 32, 2, 17, 0, 0, 0, 31, 230, 12, 143, 153, 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