Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72a35ccf7ccc0e5b145fc72593ec0afa7efd0402e0555f9c8a165a4bba320fac

Tx prefix hash: 518c2f55aab88dcf1c4a58935b9005060bbf5e39ba628da971951ba4bff1de7b
Tx public key: 6ebd58c3752b0d3d955830ba523d0f97e5350ff1d9b20519c966b5a49d4e980d
Timestamp: 1707176249 Timestamp [UCT]: 2024-02-05 23:37:29 Age [y:d:h:m:s]: 00:292:18:59:39
Block: 951228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209640 RingCT/type: yes/0
Extra: 016ebd58c3752b0d3d955830ba523d0f97e5350ff1d9b20519c966b5a49d4e980d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ba51ad1dc20398191a25555f4d299f06fef75b5d9b6f60fa2508852898f0133 0.600000000000 1409966 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": 951238, "vin": [ { "gen": { "height": 951228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ba51ad1dc20398191a25555f4d299f06fef75b5d9b6f60fa2508852898f0133" } } ], "extra": [ 1, 110, 189, 88, 195, 117, 43, 13, 61, 149, 88, 48, 186, 82, 61, 15, 151, 229, 53, 15, 241, 217, 178, 5, 25, 201, 102, 181, 164, 157, 78, 152, 13, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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