Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9d1e0cbd26fd216aeeab715f86c4760909a560c1002b6de8342119f96d16b3c

Tx prefix hash: dd567e879c6eb36ed4cabd7bda6a1349cacff3ca1e523b0cd54e5e8074ac6589
Tx public key: 67e280c0505cd8621c171fbc78c3a5dc1d6352f8eda80147a42a71e52c32f941
Timestamp: 1722087736 Timestamp [UCT]: 2024-07-27 13:42:16 Age [y:d:h:m:s]: 00:183:09:26:21
Block: 1074866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131045 RingCT/type: yes/0
Extra: 0167e280c0505cd8621c171fbc78c3a5dc1d6352f8eda80147a42a71e52c32f94102110000001391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7008a7c267872509d91ad09cbffcd64a20f76b48d8429d882b7ecae7f2923da 0.600000000000 1547385 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": 1074876, "vin": [ { "gen": { "height": 1074866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7008a7c267872509d91ad09cbffcd64a20f76b48d8429d882b7ecae7f2923da" } } ], "extra": [ 1, 103, 226, 128, 192, 80, 92, 216, 98, 28, 23, 31, 188, 120, 195, 165, 220, 29, 99, 82, 248, 237, 168, 1, 71, 164, 42, 113, 229, 44, 50, 249, 65, 2, 17, 0, 0, 0, 19, 145, 225, 60, 4, 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