Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d5e5c932e95fe44c47ac0b60d4110903bc4f6fb8dd03b44a21a85e300d0d61

Tx prefix hash: 2f37bb63bbc35f6a3da1182b96e421a636e0d1e810e4297f032b66f5f779ea6c
Tx public key: 39d141140a59192113315e7570d046ca2db7d836d0c98437ce7c738ca8ccbbc7
Timestamp: 1737575517 Timestamp [UCT]: 2025-01-22 19:51:57 Age [y:d:h:m:s]: 00:051:06:07:36
Block: 1203064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36466 RingCT/type: yes/0
Extra: 0139d141140a59192113315e7570d046ca2db7d836d0c98437ce7c738ca8ccbbc70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3280d45ceb6bf3b1e22074ee24277926b4a964d7c29329e2c1be0e3f4687a533 0.600000000000 1689737 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": 1203074, "vin": [ { "gen": { "height": 1203064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3280d45ceb6bf3b1e22074ee24277926b4a964d7c29329e2c1be0e3f4687a533" } } ], "extra": [ 1, 57, 209, 65, 20, 10, 89, 25, 33, 19, 49, 94, 117, 112, 208, 70, 202, 45, 183, 216, 54, 208, 201, 132, 55, 206, 124, 115, 140, 168, 204, 187, 199, 2, 17, 0, 0, 0, 2, 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