Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 937aa134aca1d056dc8b7001ba48962f56eda5dd5cb28b035237d5a5dbed2c74

Tx prefix hash: 913e5e6ac353085261389b0a92145b2d996d1903d566900efcc823b7e7376303
Tx public key: b44baf472d1640380eb78c45b142af8d08b1118e4b5b9d7ba5161261af562c41
Timestamp: 1716549300 Timestamp [UCT]: 2024-05-24 11:15:00 Age [y:d:h:m:s]: 01:171:22:00:13
Block: 1028961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381449 RingCT/type: yes/0
Extra: 01b44baf472d1640380eb78c45b142af8d08b1118e4b5b9d7ba5161261af562c4102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd6144cb41d9929e392a2c3dd0d3ce7bd8b27a51a09f35c5b22ddc9ea7e0969e 0.600000000000 1496962 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": 1028971, "vin": [ { "gen": { "height": 1028961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd6144cb41d9929e392a2c3dd0d3ce7bd8b27a51a09f35c5b22ddc9ea7e0969e" } } ], "extra": [ 1, 180, 75, 175, 71, 45, 22, 64, 56, 14, 183, 140, 69, 177, 66, 175, 141, 8, 177, 17, 142, 75, 91, 157, 123, 165, 22, 18, 97, 175, 86, 44, 65, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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