Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36180a2df1fff1f2c4cb1bba159064ee8e42342d3a8eb4147f30d867aa87da10

Tx prefix hash: 35c5eef64061f1b5a4def9bf52a4e4deeca8e5a4f53537782487a9c0ddf2ab58
Tx public key: b6b6a762bebd41b5aa87f7ed6747f4e33176465dbd895fb8a65e15b4abb96545
Timestamp: 1708891735 Timestamp [UCT]: 2024-02-25 20:08:55 Age [y:d:h:m:s]: 01:068:18:20:50
Block: 965464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310176 RingCT/type: yes/0
Extra: 01b6b6a762bebd41b5aa87f7ed6747f4e33176465dbd895fb8a65e15b4abb9654502110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 945624706c5cf3907b3bcc8c5edafe57373f6c76d37af6d60ea700a7fe3c5ed4 0.600000000000 1425215 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": 965474, "vin": [ { "gen": { "height": 965464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "945624706c5cf3907b3bcc8c5edafe57373f6c76d37af6d60ea700a7fe3c5ed4" } } ], "extra": [ 1, 182, 182, 167, 98, 190, 189, 65, 181, 170, 135, 247, 237, 103, 71, 244, 227, 49, 118, 70, 93, 189, 137, 95, 184, 166, 94, 21, 180, 171, 185, 101, 69, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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