Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bee9711a9885a64bd7db48a76b76a8ed904e09741c2cbcef8c0748008ed1f943

Tx prefix hash: 54a7775dac51492fee4bb0931b0aee50c9d0300c875b0daa1408b5459891b625
Tx public key: 7bce2f4f6cf5f6c4e444b769974b3afbe53076c97cca0a1c4a555077f8159dc0
Timestamp: 1774109691 Timestamp [UTC]: 2026-03-21 16:14:51 Age [y:d:h:m:s]: 00:242:21:35:35
Block: 1502735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179199 RingCT/type: yes/0
Extra: 017bce2f4f6cf5f6c4e444b769974b3afbe53076c97cca0a1c4a555077f8159dc0021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf1e228bf92f4611f3bc21953f620f73ec7fb963c1ca8e91af74e1e8480de149 0.000600000000 1992437 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 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": 1502745, "vin": [ { "gen": { "height": 1502735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf1e228bf92f4611f3bc21953f620f73ec7fb963c1ca8e91af74e1e8480de149" } } ], "extra": [ 1, 123, 206, 47, 79, 108, 245, 246, 196, 228, 68, 183, 105, 151, 75, 58, 251, 229, 48, 118, 201, 124, 202, 10, 28, 74, 85, 80, 119, 248, 21, 157, 192, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: