Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6c2aa8eb5bbcfd93fc2cda99379ad05b4ac4fd0572248a390dc4e0f4d32ff60

Tx prefix hash: 66a3a5232d5e3b14f5bd8e572c303daf4a33b9e765bcbe83a56768e5267772bc
Tx public key: d6eab80489d22a90596fa47ea09cb0c7e79c0f188ff807f4e581bda5ba8673a6
Timestamp: 1756683033 Timestamp [UCT]: 2025-08-31 23:30:33 Age [y:d:h:m:s]: 00:078:23:41:01
Block: 1358690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56433 RingCT/type: yes/0
Extra: 01d6eab80489d22a90596fa47ea09cb0c7e79c0f188ff807f4e581bda5ba8673a6021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d351e48fb7c759a41c84618622e113c61d4c674e815dd3f18aea583d6ed9e0 0.600000000000 1846703 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": 1358700, "vin": [ { "gen": { "height": 1358690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d351e48fb7c759a41c84618622e113c61d4c674e815dd3f18aea583d6ed9e0" } } ], "extra": [ 1, 214, 234, 184, 4, 137, 210, 42, 144, 89, 111, 164, 126, 160, 156, 176, 199, 231, 156, 15, 24, 143, 248, 7, 244, 229, 129, 189, 165, 186, 134, 115, 166, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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