Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49797284073753173647c9846a8aa9b9799ff723e88f53c551b71a7cd169dd4d

Tx prefix hash: c6e1f674e4621dc3a131d3f1bae15ce63d685adeb553a692a7356972ccab38f4
Tx public key: b51604ad1e8648b37f7df45402c6a20f78322bdee9ed736e1eaf7a1f8479e8ad
Timestamp: 1732821232 Timestamp [UCT]: 2024-11-28 19:13:52 Age [y:d:h:m:s]: 00:126:06:54:05
Block: 1163752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90055 RingCT/type: yes/0
Extra: 01b51604ad1e8648b37f7df45402c6a20f78322bdee9ed736e1eaf7a1f8479e8ad0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42977b8fb136dfca51429326dd0836cc9740c9b05eca9d68fff9d6c0d1706e9c 0.600000000000 1649421 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": 1163762, "vin": [ { "gen": { "height": 1163752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42977b8fb136dfca51429326dd0836cc9740c9b05eca9d68fff9d6c0d1706e9c" } } ], "extra": [ 1, 181, 22, 4, 173, 30, 134, 72, 179, 127, 125, 244, 84, 2, 198, 162, 15, 120, 50, 43, 222, 233, 237, 115, 110, 30, 175, 122, 31, 132, 121, 232, 173, 2, 17, 0, 0, 0, 6, 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