Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc03b60f07dd3ace3c05dc6bfdfb86deb6c41a2a1a308ea8755fb9917b828317

Tx prefix hash: bdca9bd59fa3235756dd874642ec1e69e9e0c44614d36e6eafdfa98245899bbf
Tx public key: 009347910f99c61754986f01388aa9a36584f3f0d0356879fe47b04bc075e70e
Timestamp: 1774151832 Timestamp [UTC]: 2026-03-22 03:57:12 Age [y:d:h:m:s]: 00:238:22:17:47
Block: 1503093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176231 RingCT/type: yes/0
Extra: 01009347910f99c61754986f01388aa9a36584f3f0d0356879fe47b04bc075e70e021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9551fda7290174c3ee2a1ce02eab0e800ae11529b4bba0e0fd6295a8cd200c69 0.000600000000 1992797 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": 1503103, "vin": [ { "gen": { "height": 1503093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9551fda7290174c3ee2a1ce02eab0e800ae11529b4bba0e0fd6295a8cd200c69" } } ], "extra": [ 1, 0, 147, 71, 145, 15, 153, 198, 23, 84, 152, 111, 1, 56, 138, 169, 163, 101, 132, 243, 240, 208, 53, 104, 121, 254, 71, 176, 75, 192, 117, 231, 14, 2, 17, 0, 0, 0, 1, 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: