Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16348c718a7f6a2f1982406e164c6aa720437a64b6eb2b8e76f2e5c7a26adab3

Tx prefix hash: e64c56d940dfbbcaa6d3a03ceadb840a7e7db0dc9673d117a70a09e549ab62dd
Tx public key: 48926dd24b3f447afabe54d8f095410a714cc3990812b70157a71441646af61c
Timestamp: 1719445145 Timestamp [UCT]: 2024-06-26 23:39:05 Age [y:d:h:m:s]: 00:289:20:51:42
Block: 1052947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207136 RingCT/type: yes/0
Extra: 0148926dd24b3f447afabe54d8f095410a714cc3990812b70157a71441646af61c02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 035de4ea727f0bfe1b7f5b7189ca2f7e4306f8df51f7e9ec0eef368f75e69916 0.600000000000 1523292 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": 1052957, "vin": [ { "gen": { "height": 1052947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "035de4ea727f0bfe1b7f5b7189ca2f7e4306f8df51f7e9ec0eef368f75e69916" } } ], "extra": [ 1, 72, 146, 109, 210, 75, 63, 68, 122, 250, 190, 84, 216, 240, 149, 65, 10, 113, 76, 195, 153, 8, 18, 183, 1, 87, 167, 20, 65, 100, 106, 246, 28, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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