Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e123c371d9b6060eb30bf4d0f72305ab857012794f679d776a872a999c3d02c

Tx prefix hash: 2e220d248bb0506c41286d483dc5b60e739bd9a242dd4a73c6faf2a12d55bc57
Tx public key: c530351e432f3c8c14a028d548ffe872c9be11b053b18f5f7a062faa854cf090
Timestamp: 1695361114 Timestamp [UCT]: 2023-09-22 05:38:34 Age [y:d:h:m:s]: 02:044:00:48:12
Block: 853482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551122 RingCT/type: yes/0
Extra: 01c530351e432f3c8c14a028d548ffe872c9be11b053b18f5f7a062faa854cf0900211000000034b8f5122000000000000000000

1 output(s) for total of 0.912136612000 dcy

stealth address amount amount idx
00: f90ae836f8d7da3d93376d6a3d8bb6d99cd3bae652495caeb87a473708747642 0.912136612000 1307390 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": 853492, "vin": [ { "gen": { "height": 853482 } } ], "vout": [ { "amount": 912136612, "target": { "key": "f90ae836f8d7da3d93376d6a3d8bb6d99cd3bae652495caeb87a473708747642" } } ], "extra": [ 1, 197, 48, 53, 30, 67, 47, 60, 140, 20, 160, 40, 213, 72, 255, 232, 114, 201, 190, 17, 176, 83, 177, 143, 95, 122, 6, 47, 170, 133, 76, 240, 144, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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