Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 591aaa5c51ce3a0efbd2869e71a5f28ac277290dee065f688e8b7ca9995c1d9d

Tx prefix hash: 7bce9f273e1ede028fcc9d4e736f48ad6a5764c985d1531ad048881ee0f3ca84
Tx public key: 1c87e72013d3e36a2450b70029930e27823d78518966f7a404be74853f5f1de6
Timestamp: 1736713589 Timestamp [UCT]: 2025-01-12 20:26:29 Age [y:d:h:m:s]: 00:156:15:46:38
Block: 1195973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111679 RingCT/type: yes/0
Extra: 011c87e72013d3e36a2450b70029930e27823d78518966f7a404be74853f5f1de60211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28f4a835540e76e188a4b750d0c4a4d2bc4fcdbb2f3faafba4d351f4dec71169 0.600000000000 1682570 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": 1195983, "vin": [ { "gen": { "height": 1195973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28f4a835540e76e188a4b750d0c4a4d2bc4fcdbb2f3faafba4d351f4dec71169" } } ], "extra": [ 1, 28, 135, 231, 32, 19, 211, 227, 106, 36, 80, 183, 0, 41, 147, 14, 39, 130, 61, 120, 81, 137, 102, 247, 164, 4, 190, 116, 133, 63, 95, 29, 230, 2, 17, 0, 0, 0, 9, 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