Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 958d4af02f84e05a8c33dd4f69b37fb2467e3328ca577b9ff6c8c7ec33f03aec

Tx prefix hash: bf339488c87cf9e5e7538d5e1a2610c8287cd528f21f69d643559ada333271eb
Tx public key: 7db2178501ea80fcb5e301289631dd46a69a0daa8c570fd5a5a08e174d056561
Timestamp: 1742023458 Timestamp [UTC]: 2025-03-15 07:24:18 Age [y:d:h:m:s]: 01:246:17:39:46
Block: 1239690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440350 RingCT/type: yes/0
Extra: 017db2178501ea80fcb5e301289631dd46a69a0daa8c570fd5a5a08e174d0565610211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: af2501e6a1b15a97a570a9ec2e1e7da438e4d150841b076db99ce7b60c4aa7c6 0.000600000000 1726655 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": 1239700, "vin": [ { "gen": { "height": 1239690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af2501e6a1b15a97a570a9ec2e1e7da438e4d150841b076db99ce7b60c4aa7c6" } } ], "extra": [ 1, 125, 178, 23, 133, 1, 234, 128, 252, 181, 227, 1, 40, 150, 49, 221, 70, 166, 154, 13, 170, 140, 87, 15, 213, 165, 160, 142, 23, 77, 5, 101, 97, 2, 17, 0, 0, 0, 8, 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: