Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b054c4dd417d51548dba0cfa2cbb93ae327a326de9d3d3f36608ab5e655758

Tx prefix hash: 42dc5867ffa564f358e54bf185cd1fa1f6a4074f4c46153512704902ea20572e
Tx public key: 25c19b95feab40c8bcb95c054aacfe7fffd8352e21f25740b6bf8a6384b6b41d
Timestamp: 1705204076 Timestamp [UCT]: 2024-01-14 03:47:56 Age [y:d:h:m:s]: 01:323:21:30:47
Block: 934868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490353 RingCT/type: yes/0
Extra: 0125c19b95feab40c8bcb95c054aacfe7fffd8352e21f25740b6bf8a6384b6b41d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 787e1b71dbe8c0148e39c5e21b9faec779b888dba22102f91e904e04c36da0f2 0.600000000000 1392884 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": 934878, "vin": [ { "gen": { "height": 934868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "787e1b71dbe8c0148e39c5e21b9faec779b888dba22102f91e904e04c36da0f2" } } ], "extra": [ 1, 37, 193, 155, 149, 254, 171, 64, 200, 188, 185, 92, 5, 74, 172, 254, 127, 255, 216, 53, 46, 33, 242, 87, 64, 182, 191, 138, 99, 132, 182, 180, 29, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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