Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa8c78a9be05a628820583f6032214a68a2c0bf9fc0c3cb5d5a89fd5ead379d3

Tx prefix hash: 894f5943237286d9d70e3cbd766334be37ec632a2f376991d4ab4b6a8759a5d4
Tx public key: c901f3788bf45105a6fac8b1f94dd52b870a59e5f3a650b54ba76c3b9cd6bd10
Timestamp: 1646794948 Timestamp [UTC]: 2022-03-09 03:02:28 Age [y:d:h:m:s]: 04:064:04:34:58
Block: 454394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1077135 RingCT/type: yes/0
Extra: 01c901f3788bf45105a6fac8b1f94dd52b870a59e5f3a650b54ba76c3b9cd6bd100211000000024a0f5013000000000000000000

1 output(s) for total of 0.019162719018 xmr

stealth address amount amount idx tag
00: bcd27faf098aa11ea8209b083662657d5f3034a0cad3aff0f68a13c5aafa3447 0.019162719018 870033 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": 454404, "vin": [ { "gen": { "height": 454394 } } ], "vout": [ { "amount": 19162719018, "target": { "key": "bcd27faf098aa11ea8209b083662657d5f3034a0cad3aff0f68a13c5aafa3447" } } ], "extra": [ 1, 201, 1, 243, 120, 139, 244, 81, 5, 166, 250, 200, 177, 249, 77, 213, 43, 135, 10, 89, 229, 243, 166, 80, 181, 75, 167, 108, 59, 156, 214, 189, 16, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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: