Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b2736536ea7f9687f240dffdcb2a9358f43ae0483a54228751ed4166124303

Tx prefix hash: 6a01c8a931cbc25f10cc64b48b31a991c02074ea2f6cf62c8243db1565d966dc
Tx public key: 926a7922a60a7fa4f9587ffff2ccbab744ab82625341e87323080a617c9f002d
Timestamp: 1722372271 Timestamp [UCT]: 2024-07-30 20:44:31 Age [y:d:h:m:s]: 01:108:08:32:48
Block: 1077216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335940 RingCT/type: yes/0
Extra: 01926a7922a60a7fa4f9587ffff2ccbab744ab82625341e87323080a617c9f002d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8631c9d2f6bb603ef0fcb0a2a18c5a625769c9e5828522c6c4fdf071acaa17e4 0.600000000000 1549763 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": 1077226, "vin": [ { "gen": { "height": 1077216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8631c9d2f6bb603ef0fcb0a2a18c5a625769c9e5828522c6c4fdf071acaa17e4" } } ], "extra": [ 1, 146, 106, 121, 34, 166, 10, 127, 164, 249, 88, 127, 255, 242, 204, 186, 183, 68, 171, 130, 98, 83, 65, 232, 115, 35, 8, 10, 97, 124, 159, 0, 45, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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