Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8324d205144ccf0e89dfb79e5109281cabbf9b023a54ecfc6984551081ed10

Tx prefix hash: 2159aea6608ff1a0049722337104fdc13d6069b467f275d7408fe9bac69edb86
Tx public key: d3648e653d9a8eaef3f0dce60ce24c2ab74e50ac4397274fe877a1c247eb5d7e
Timestamp: 1706345763 Timestamp [UCT]: 2024-01-27 08:56:03 Age [y:d:h:m:s]: 01:074:17:08:42
Block: 944331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314486 RingCT/type: yes/0
Extra: 01d3648e653d9a8eaef3f0dce60ce24c2ab74e50ac4397274fe877a1c247eb5d7e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb2b2f3ad30ee6fa0d4d4cb86caa5247ab0fa5a7f233f2f13d245e337c3e384a 0.600000000000 1402567 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": 944341, "vin": [ { "gen": { "height": 944331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb2b2f3ad30ee6fa0d4d4cb86caa5247ab0fa5a7f233f2f13d245e337c3e384a" } } ], "extra": [ 1, 211, 100, 142, 101, 61, 154, 142, 174, 243, 240, 220, 230, 12, 226, 76, 42, 183, 78, 80, 172, 67, 151, 39, 79, 232, 119, 161, 194, 71, 235, 93, 126, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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