Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d04754dbabaaf5176d3e93e453e7b552e6843adaee7f55b2511bb510bc84e0f

Tx prefix hash: 5b4f8b907902cfda0c3886f67c9964b152301f883cfc20e0fbef897832c2f606
Tx public key: 6a38ed3632769514951586929c0e72273b4c93dc81e2d5b2d0b23fe1dae8fc18
Timestamp: 1773791230 Timestamp [UTC]: 2026-03-17 23:47:10 Age [y:d:h:m:s]: 00:241:13:35:23
Block: 1500109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178060 RingCT/type: yes/0
Extra: 016a38ed3632769514951586929c0e72273b4c93dc81e2d5b2d0b23fe1dae8fc18021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6eddbcc0c0fc702788bcb7481952f7b279160ec6e78d21c34c1cb50263d0442 0.000600000000 1989779 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": 1500119, "vin": [ { "gen": { "height": 1500109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6eddbcc0c0fc702788bcb7481952f7b279160ec6e78d21c34c1cb50263d0442" } } ], "extra": [ 1, 106, 56, 237, 54, 50, 118, 149, 20, 149, 21, 134, 146, 156, 14, 114, 39, 59, 76, 147, 220, 129, 226, 213, 178, 208, 178, 63, 225, 218, 232, 252, 24, 2, 17, 0, 0, 0, 7, 228, 245, 25, 63, 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: