Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7590d5021d59720633a0f8cb808d6ccc46964ecfd8262db495cbccfa780c9d93

Tx prefix hash: c6349ac20af7750809e4ce5939ebd2fba11ccdb9171d3a2215a016e5c7b8a02d
Tx public key: b5148bf1445b84e62c2d2289b28680e0da365e3717156c86cda70ee7f9c98f97
Timestamp: 1710676586 Timestamp [UCT]: 2024-03-17 11:56:26 Age [y:d:h:m:s]: 01:038:05:23:19
Block: 980280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288299 RingCT/type: yes/0
Extra: 01b5148bf1445b84e62c2d2289b28680e0da365e3717156c86cda70ee7f9c98f970211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d3a0fc6b5a420aef1ff64a1c0da23e43221ceb11b78c8d6568d38d2ab5f0119 0.600000000000 1440345 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": 980290, "vin": [ { "gen": { "height": 980280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d3a0fc6b5a420aef1ff64a1c0da23e43221ceb11b78c8d6568d38d2ab5f0119" } } ], "extra": [ 1, 181, 20, 139, 241, 68, 91, 132, 230, 44, 45, 34, 137, 178, 134, 128, 224, 218, 54, 94, 55, 23, 21, 108, 134, 205, 167, 14, 231, 249, 201, 143, 151, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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