Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df815e80284a61c7ff91b77a7977542b02c4f53129520cd1e5e0b6973fb7a5b1

Tx prefix hash: be6b1665442bcd64c467da88bf4054d2f9f570cd9b06f7ceb661667236e041e8
Tx public key: 2cf2940b21d8500da34f4f7e3dfbf83d64c07db17e2a12bead39c91c2f5742e9
Timestamp: 1696266095 Timestamp [UCT]: 2023-10-02 17:01:35 Age [y:d:h:m:s]: 01:190:15:31:09
Block: 860998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397299 RingCT/type: yes/0
Extra: 012cf2940b21d8500da34f4f7e3dfbf83d64c07db17e2a12bead39c91c2f5742e90211000000034b8f5122000000000000000000

1 output(s) for total of 0.861303574000 dcy

stealth address amount amount idx
00: 606a24481f62b5a103061aa44922c6bb35fb1523e78be1f601785419f0b0a3e9 0.861303574000 1315310 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": 861008, "vin": [ { "gen": { "height": 860998 } } ], "vout": [ { "amount": 861303574, "target": { "key": "606a24481f62b5a103061aa44922c6bb35fb1523e78be1f601785419f0b0a3e9" } } ], "extra": [ 1, 44, 242, 148, 11, 33, 216, 80, 13, 163, 79, 79, 126, 61, 251, 248, 61, 100, 192, 125, 177, 126, 42, 18, 190, 173, 57, 201, 28, 47, 87, 66, 233, 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