Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498c561787170e060ba1cb46f364ec66fc430d3bc8122214ec4de434e526142c

Tx prefix hash: f82b2dc0469aab413bbafa58af6239ee59678dbb0c55a40d2df9de01f8415f96
Tx public key: a9c48b434b52ef09c941b9b4b5f5d5e215a2d612fa67c3db1eb5064d0b84f4f8
Timestamp: 1636146512 Timestamp [UCT]: 2021-11-05 21:08:32 Age [y:d:h:m:s]: 03:196:03:56:09
Block: 368106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918586 RingCT/type: yes/0
Extra: 01a9c48b434b52ef09c941b9b4b5f5d5e215a2d612fa67c3db1eb5064d0b84f4f80211000000084a0f5013000000000000000000

1 output(s) for total of 37.010071246000 dcy

stealth address amount amount idx
00: a6df9ec4970ac95a8eecd5b5f3c22b0260549feda983f50e236a992b6410dd79 37.010071246000 746718 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 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": 368116, "vin": [ { "gen": { "height": 368106 } } ], "vout": [ { "amount": 37010071246, "target": { "key": "a6df9ec4970ac95a8eecd5b5f3c22b0260549feda983f50e236a992b6410dd79" } } ], "extra": [ 1, 169, 196, 139, 67, 75, 82, 239, 9, 201, 65, 185, 180, 181, 245, 213, 226, 21, 162, 214, 18, 250, 103, 195, 219, 30, 181, 6, 77, 11, 132, 244, 248, 2, 17, 0, 0, 0, 8, 74, 15, 80, 19, 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