Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05638479530a76d0efef3b28e669a19589879f1e2ed394d36b7f9676f572f338

Tx prefix hash: c965f49eef0eea79d937bec42af7f1f5ea774e83b3c213cec795a92f0546401b
Tx public key: b64256399ba2ba4fe2fdd4eb5d8dde9361558bbc52b73624e20d411621612c72
Timestamp: 1695427821 Timestamp [UCT]: 2023-09-23 00:10:21 Age [y:d:h:m:s]: 02:044:20:57:50
Block: 854039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551707 RingCT/type: yes/0
Extra: 01b64256399ba2ba4fe2fdd4eb5d8dde9361558bbc52b73624e20d411621612c72021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.908268631000 dcy

stealth address amount amount idx
00: e21de20e51447bb16626e3de5f759f4c891b4d4c9acecf0e2a2fee9687ced078 0.908268631000 1307989 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": 854049, "vin": [ { "gen": { "height": 854039 } } ], "vout": [ { "amount": 908268631, "target": { "key": "e21de20e51447bb16626e3de5f759f4c891b4d4c9acecf0e2a2fee9687ced078" } } ], "extra": [ 1, 182, 66, 86, 57, 155, 162, 186, 79, 226, 253, 212, 235, 93, 141, 222, 147, 97, 85, 139, 188, 82, 183, 54, 36, 226, 13, 65, 22, 33, 97, 44, 114, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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