Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da193aaad76c555f83a201e38e8147c351e3173466956d9fb1389e6264aa01e2

Tx prefix hash: 8d8c6af0079324eb1a05b6505fe0f413f0554994f59a60a756a1476f4b5f0028
Tx public key: deda8d6b2a4ac72c20e61a1013628e87a253e0857b2690abf066825fdb04758e
Timestamp: 1736633569 Timestamp [UCT]: 2025-01-11 22:12:49 Age [y:d:h:m:s]: 00:067:01:14:21
Block: 1195311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47721 RingCT/type: yes/0
Extra: 01deda8d6b2a4ac72c20e61a1013628e87a253e0857b2690abf066825fdb04758e0211000000191f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83e7ef02dcbd51a69e2c7f17d07dabb39fe3c4985cc9e2dcdd1540e5a9ec8826 0.600000000000 1681900 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": 1195321, "vin": [ { "gen": { "height": 1195311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83e7ef02dcbd51a69e2c7f17d07dabb39fe3c4985cc9e2dcdd1540e5a9ec8826" } } ], "extra": [ 1, 222, 218, 141, 107, 42, 74, 199, 44, 32, 230, 26, 16, 19, 98, 142, 135, 162, 83, 224, 133, 123, 38, 144, 171, 240, 102, 130, 95, 219, 4, 117, 142, 2, 17, 0, 0, 0, 25, 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