Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d01c53146144bc7408b04e88d7ec032ea6f098b4b0901e0e5e8441e22483d403

Tx prefix hash: 97fdef8b7e193b49307cf4b92e7354f1bc0aa8041de678a367b8fc9e4ba58a24
Tx public key: 1b6bfba14b4cbefada5ef468cba0d0f8048541908607d7643d751b95c692d031
Timestamp: 1729145691 Timestamp [UCT]: 2024-10-17 06:14:51 Age [y:d:h:m:s]: 00:148:09:22:26
Block: 1133383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105834 RingCT/type: yes/0
Extra: 011b6bfba14b4cbefada5ef468cba0d0f8048541908607d7643d751b95c692d0310211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a71548d8bc32b0f8162875fa3a95772aa951af7ad8aa45a6c25d746656b18d6 0.600000000000 1616490 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": 1133393, "vin": [ { "gen": { "height": 1133383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a71548d8bc32b0f8162875fa3a95772aa951af7ad8aa45a6c25d746656b18d6" } } ], "extra": [ 1, 27, 107, 251, 161, 75, 76, 190, 250, 218, 94, 244, 104, 203, 160, 208, 248, 4, 133, 65, 144, 134, 7, 215, 100, 61, 117, 27, 149, 198, 146, 208, 49, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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