Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f015edd484c3f1458258a0e9368adb553e97d3541817bbc8e66c6d1766d829a

Tx prefix hash: 001a13b1ef6f07d577f755a4040955dcaade0dfc4399e26006cf538c6a2fab9b
Tx public key: 504c273dc34e5aa03929f5411dae5817f699a64afd3dc1bdfae508098f07b964
Timestamp: 1645909145 Timestamp [UCT]: 2022-02-26 20:59:05 Age [y:d:h:m:s]: 03:027:23:08:33
Block: 447158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 800031 RingCT/type: yes/0
Extra: 01504c273dc34e5aa03929f5411dae5817f699a64afd3dc1bdfae508098f07b96402110000002a2e6b1fd5000000000000000000

1 output(s) for total of 20.247910143000 dcy

stealth address amount amount idx
00: 448767c530dcfbd05b1c07016b4c8b57c90548a44ba5f28d0b3e3fa3ce3c4f48 20.247910143000 861239 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": 447168, "vin": [ { "gen": { "height": 447158 } } ], "vout": [ { "amount": 20247910143, "target": { "key": "448767c530dcfbd05b1c07016b4c8b57c90548a44ba5f28d0b3e3fa3ce3c4f48" } } ], "extra": [ 1, 80, 76, 39, 61, 195, 78, 90, 160, 57, 41, 245, 65, 29, 174, 88, 23, 246, 153, 166, 74, 253, 61, 193, 189, 250, 229, 8, 9, 143, 7, 185, 100, 2, 17, 0, 0, 0, 42, 46, 107, 31, 213, 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