Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 956c8b8dfa3be76d946efa6dcdc005066ea2e8785f25b6a23d825cc6ea8c00d6

Tx prefix hash: 3a955c66d20598ab6bfbfa6163bddafda80ca677692678f1a1b123be1259cb5c
Tx public key: 4cbb84de419a7a109acb1e10d4b13b4ce371969e31d5ab2a83239dc80ec8be49
Timestamp: 1660470274 Timestamp [UTC]: 2022-08-14 09:44:34 Age [y:d:h:m:s]: 04:094:12:58:29
Block: 565590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1113623 RingCT/type: yes/0
Extra: 014cbb84de419a7a109acb1e10d4b13b4ce371969e31d5ab2a83239dc80ec8be49021100000001ec6d1a1a000000000000000000

1 output(s) for total of 0.008202866657 xmr

stealth address amount amount idx tag
00: d7a9017bb79717a0277565fd333a54f776a8d32ffb1a109a9a37dc1b3b24e765 0.008202866657 998496 of 0 -

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 dinastycoin-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": 565600, "vin": [ { "gen": { "height": 565590 } } ], "vout": [ { "amount": 8202866657, "target": { "key": "d7a9017bb79717a0277565fd333a54f776a8d32ffb1a109a9a37dc1b3b24e765" } } ], "extra": [ 1, 76, 187, 132, 222, 65, 154, 122, 16, 154, 203, 30, 16, 212, 177, 59, 76, 227, 113, 150, 158, 49, 213, 171, 42, 131, 35, 157, 200, 14, 200, 190, 73, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: