Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0becb54e125dbb810daa7b4cac3a67a1c49da081f75e4bf5ea4317f1f1ea3c

Tx prefix hash: f30826d2fbdc9466dc28419e06f5c9c5a8772055d131ab306453135205d8225e
Tx public key: 5db49a866e89ff27f419e19d1f6e54866e1a6ab06bd215584ea3b6f34c8fdfb0
Timestamp: 1742150697 Timestamp [UTC]: 2025-03-16 18:44:57 Age [y:d:h:m:s]: 01:247:11:25:08
Block: 1240737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440952 RingCT/type: yes/0
Extra: 015db49a866e89ff27f419e19d1f6e54866e1a6ab06bd215584ea3b6f34c8fdfb002110000002d1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 839638f835c3644896c106444242812c61274b5c157b68ed008947435e8c17cf 0.000600000000 1727710 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": 1240747, "vin": [ { "gen": { "height": 1240737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "839638f835c3644896c106444242812c61274b5c157b68ed008947435e8c17cf" } } ], "extra": [ 1, 93, 180, 154, 134, 110, 137, 255, 39, 244, 25, 225, 157, 31, 110, 84, 134, 110, 26, 106, 176, 107, 210, 21, 88, 78, 163, 182, 243, 76, 143, 223, 176, 2, 17, 0, 0, 0, 45, 31, 10, 83, 235, 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: