Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534e345f642f45df1588f4b35cf1e12133d0cafb2bf9d3bbe95c5193553efb7b

Tx prefix hash: 44e560f2b891b02dd47acba6b917b44bda2dfd869d4bacf0abc2758224a88e40
Tx public key: 83e2d75e65fdb0491d8d955a760bf7c1fd029cf5b1996d2479cf1e66e4c23705
Timestamp: 1742021286 Timestamp [UCT]: 2025-03-15 06:48:06 Age [y:d:h:m:s]: 00:296:16:12:17
Block: 1239671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209840 RingCT/type: yes/0
Extra: 0183e2d75e65fdb0491d8d955a760bf7c1fd029cf5b1996d2479cf1e66e4c237050211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3fda65c288509ecaec95ae182d5ee5e4c4fd5485f1fb75f7b42220582196dd1 0.600000000000 1726636 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": 1239681, "vin": [ { "gen": { "height": 1239671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3fda65c288509ecaec95ae182d5ee5e4c4fd5485f1fb75f7b42220582196dd1" } } ], "extra": [ 1, 131, 226, 215, 94, 101, 253, 176, 73, 29, 141, 149, 90, 118, 11, 247, 193, 253, 2, 156, 245, 177, 153, 109, 36, 121, 207, 30, 102, 228, 194, 55, 5, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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