Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a96d1b4800c29839a89cd0761a4e68f703a542335db1958d21c90bb704481a9f

Tx prefix hash: daa5ec3cf2e19d3748179e4a506b5a914afcfc692589c59129556dd6b7084bf3
Tx public key: 9f1b75ba65e01caba5d7c4091e42132804917f2ddf2f32b00efcd6363cda5ff1
Timestamp: 1709006521 Timestamp [UCT]: 2024-02-27 04:02:01 Age [y:d:h:m:s]: 01:051:22:09:15
Block: 966419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298129 RingCT/type: yes/0
Extra: 019f1b75ba65e01caba5d7c4091e42132804917f2ddf2f32b00efcd6363cda5ff10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dd07d1e0f1e28d292c169301598bba2edeaeadc43bb59f829fee9ad9d4f3b1c 0.600000000000 1426176 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": 966429, "vin": [ { "gen": { "height": 966419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dd07d1e0f1e28d292c169301598bba2edeaeadc43bb59f829fee9ad9d4f3b1c" } } ], "extra": [ 1, 159, 27, 117, 186, 101, 224, 28, 171, 165, 215, 196, 9, 30, 66, 19, 40, 4, 145, 127, 45, 223, 47, 50, 176, 14, 252, 214, 54, 60, 218, 95, 241, 2, 17, 0, 0, 0, 4, 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