Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653c6fe95abe8f4d72443472160ef10b3c9bbe3f2bc5d8edb88bd263a1a06750

Tx prefix hash: aae88ebf7a72925093232dc73245e76d2f49328347bfd941522b4597d163cc87
Tx public key: 2d30c741c12980fa7d18a51a8e513f9277b9d34fc9938bcbf14063b6b4bd9ae4
Timestamp: 1638731532 Timestamp [UCT]: 2021-12-05 19:12:12 Age [y:d:h:m:s]: 03:099:20:05:00
Block: 389137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 850067 RingCT/type: yes/0
Extra: 012d30c741c12980fa7d18a51a8e513f9277b9d34fc9938bcbf14063b6b4bd9ae40211000000021cab2639000000000000000000

1 output(s) for total of 31.523029462000 dcy

stealth address amount amount idx
00: 13aaf89876082261043f00f71aaba5828c63fe0eec7d882d9898055e348b690a 31.523029462000 784164 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": 389147, "vin": [ { "gen": { "height": 389137 } } ], "vout": [ { "amount": 31523029462, "target": { "key": "13aaf89876082261043f00f71aaba5828c63fe0eec7d882d9898055e348b690a" } } ], "extra": [ 1, 45, 48, 199, 65, 193, 41, 128, 250, 125, 24, 165, 26, 142, 81, 63, 146, 119, 185, 211, 79, 201, 147, 139, 203, 241, 64, 99, 182, 180, 189, 154, 228, 2, 17, 0, 0, 0, 2, 28, 171, 38, 57, 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