Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34d029bf1e84b42821bc6ec7853237f8e0103cabd63b7133cee7159e9d472ff1

Tx prefix hash: 6dbf4a5c0ec4c2fa5b5af47947e79b6ebd91464a10e127ee75fe033d25dd80a4
Tx public key: d2c08bbbe4d340b1e9aa1e40fef08b933e64c6fe8e15731358c9ca3c9eef0fd3
Timestamp: 1737574418 Timestamp [UCT]: 2025-01-22 19:33:38 Age [y:d:h:m:s]: 00:146:06:31:30
Block: 1203058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104284 RingCT/type: yes/0
Extra: 01d2c08bbbe4d340b1e9aa1e40fef08b933e64c6fe8e15731358c9ca3c9eef0fd30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ba8abf4e1d9dce207eea4d7ecdb87b1b8d76ecfd50a34aa98057e0602d9156f 0.600000000000 1689731 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": 1203068, "vin": [ { "gen": { "height": 1203058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ba8abf4e1d9dce207eea4d7ecdb87b1b8d76ecfd50a34aa98057e0602d9156f" } } ], "extra": [ 1, 210, 192, 139, 187, 228, 211, 64, 177, 233, 170, 30, 64, 254, 240, 139, 147, 62, 100, 198, 254, 142, 21, 115, 19, 88, 201, 202, 60, 158, 239, 15, 211, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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