Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e231a2611a52557ec6cb5f3e2474422e2aa31d4e8fd75719cd9673f32487c701

Tx prefix hash: b1efca42c71e3e399b8592f28704622db9b8f5b8cc0f944aad26c61affd714b1
Tx public key: 6728c405ac30fe913aa29423636e7bdae34f93932971544c343866d67a36b434
Timestamp: 1709190853 Timestamp [UCT]: 2024-02-29 07:14:13 Age [y:d:h:m:s]: 01:107:20:58:03
Block: 967954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338042 RingCT/type: yes/0
Extra: 016728c405ac30fe913aa29423636e7bdae34f93932971544c343866d67a36b4340211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20bba91b6c247d7381cafd6ce3d09db9c4585c1d630f7abed4ba2b661416f8ae 0.600000000000 1427749 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": 967964, "vin": [ { "gen": { "height": 967954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20bba91b6c247d7381cafd6ce3d09db9c4585c1d630f7abed4ba2b661416f8ae" } } ], "extra": [ 1, 103, 40, 196, 5, 172, 48, 254, 145, 58, 162, 148, 35, 99, 110, 123, 218, 227, 79, 147, 147, 41, 113, 84, 76, 52, 56, 102, 214, 122, 54, 180, 52, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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