Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bca134fe006ad419cf7621f284cdcb96a58ee7dc72dfdf55a778359454bd1548

Tx prefix hash: b2bb15e59a96a800c278991579f6fcf83e6c9ae2a0685c7932c3c8f045197eeb
Tx public key: d15071daa22a59080cd424e4ce17d238eb8582b76a974dd31747555b2b62c63c
Timestamp: 1773004373 Timestamp [UTC]: 2026-03-08 21:12:53 Age [y:d:h:m:s]: 00:256:22:46:49
Block: 1493617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189291 RingCT/type: yes/0
Extra: 01d15071daa22a59080cd424e4ce17d238eb8582b76a974dd31747555b2b62c63c021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cefe23125b84f7fe3b2761754b44f0d90e8b3d0660a469a87d6e977fc4fb6c83 0.000600000000 1983177 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": 1493627, "vin": [ { "gen": { "height": 1493617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cefe23125b84f7fe3b2761754b44f0d90e8b3d0660a469a87d6e977fc4fb6c83" } } ], "extra": [ 1, 209, 80, 113, 218, 162, 42, 89, 8, 12, 212, 36, 228, 206, 23, 210, 56, 235, 133, 130, 183, 106, 151, 77, 211, 23, 71, 85, 91, 43, 98, 198, 60, 2, 17, 0, 0, 0, 3, 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: