Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbdb6f101b913108f4fd24936893cf9d352606694b982b5ad7597a0a6bd2af90

Tx prefix hash: 0e720f12793de1657787408f9f43324cdf666afd0edbde8c086316097b5c4bf1
Tx public key: 2f8887f061384dc7f63e86a0b6b93f9d86786e9f4a45f5e7de2253dd130e939b
Timestamp: 1650531076 Timestamp [UTC]: 2022-04-21 08:51:16 Age [y:d:h:m:s]: 04:216:09:00:11
Block: 484850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1198644 RingCT/type: yes/0
Extra: 012f8887f061384dc7f63e86a0b6b93f9d86786e9f4a45f5e7de2253dd130e939b02110000000233af99f4000000000000000000

1 output(s) for total of 0.015187661423 xmr

stealth address amount amount idx tag
00: 6636dc9f6998dfe67721331a4150f5d8a47125f3f3a4a953b6423a09bee50da1 0.015187661423 906809 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": 484860, "vin": [ { "gen": { "height": 484850 } } ], "vout": [ { "amount": 15187661423, "target": { "key": "6636dc9f6998dfe67721331a4150f5d8a47125f3f3a4a953b6423a09bee50da1" } } ], "extra": [ 1, 47, 136, 135, 240, 97, 56, 77, 199, 246, 62, 134, 160, 182, 185, 63, 157, 134, 120, 110, 159, 74, 69, 245, 231, 222, 34, 83, 221, 19, 14, 147, 155, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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: