Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8b7af6614e8dee5f3f1d3a124fa4093ebe11b554ff6229a2a7159a768485342

Tx prefix hash: 64e121561873961248058ae8f2494e610d7e7886059e1fde4726ddbc780a888b
Tx public key: ae1e9b64b522f76dfd9f91c772f077b22e1df1dd0adc5f62378789f11322db88
Timestamp: 1723391672 Timestamp [UCT]: 2024-08-11 15:54:32 Age [y:d:h:m:s]: 01:094:16:57:54
Block: 1085676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326164 RingCT/type: yes/0
Extra: 01ae1e9b64b522f76dfd9f91c772f077b22e1df1dd0adc5f62378789f11322db88021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a0892a5910e53ec7872a595f4de4eccb4e325b650146bda857e0bda7051d932 0.600000000000 1560265 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": 1085686, "vin": [ { "gen": { "height": 1085676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a0892a5910e53ec7872a595f4de4eccb4e325b650146bda857e0bda7051d932" } } ], "extra": [ 1, 174, 30, 155, 100, 181, 34, 247, 109, 253, 159, 145, 199, 114, 240, 119, 178, 46, 29, 241, 221, 10, 220, 95, 98, 55, 135, 137, 241, 19, 34, 219, 136, 2, 17, 0, 0, 0, 9, 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