Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b06e6e7383edf3cbccfef3d246f84568f1a84541e747c27eed5dd69e149faa

Tx prefix hash: b52066bf2ebf00324115d8b138cea155269bef8f8a27cb44379e4de28ac0ad97
Tx public key: 1d7c459063fde0dcfe73584457228e7f6ca76951ab50737d0a30cfb20cbf45ac
Timestamp: 1774630207 Timestamp [UTC]: 2026-03-27 16:50:07 Age [y:d:h:m:s]: 00:235:10:37:41
Block: 1507062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173789 RingCT/type: yes/0
Extra: 011d7c459063fde0dcfe73584457228e7f6ca76951ab50737d0a30cfb20cbf45ac021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb31dc35c5c9cc46da8af3da4cf86c32618786a0b4ce586ef3afccc59dfa47f8 0.000600000000 1996814 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": 1507072, "vin": [ { "gen": { "height": 1507062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb31dc35c5c9cc46da8af3da4cf86c32618786a0b4ce586ef3afccc59dfa47f8" } } ], "extra": [ 1, 29, 124, 69, 144, 99, 253, 224, 220, 254, 115, 88, 68, 87, 34, 142, 127, 108, 167, 105, 81, 171, 80, 115, 125, 10, 48, 207, 178, 12, 191, 69, 172, 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: