Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b87bfe741638b1f1abe0b7bebbeefcc0b136fb0101e5a8b1cf07d597812f3707

Tx prefix hash: 771e966be1fcdc7fc055b8b92241151d21c9e89480db4c2288a040e1ab80257d
Tx public key: 478c3e12de456f9993d3b0dafa29d0f8e8c86f41adcb0b35ca6cf512ce368924
Timestamp: 1748731290 Timestamp [UTC]: 2025-05-31 22:41:30 Age [y:d:h:m:s]: 01:169:01:45:28
Block: 1295211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384808 RingCT/type: yes/0
Extra: 01478c3e12de456f9993d3b0dafa29d0f8e8c86f41adcb0b35ca6cf512ce36892402110000000843846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b23c1995a11289b8c1e9e4d16b503fa4e4ae3e4700c714ea37baff6dcae9c75c 0.000600000000 1782714 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": 1295221, "vin": [ { "gen": { "height": 1295211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b23c1995a11289b8c1e9e4d16b503fa4e4ae3e4700c714ea37baff6dcae9c75c" } } ], "extra": [ 1, 71, 140, 62, 18, 222, 69, 111, 153, 147, 211, 176, 218, 250, 41, 208, 248, 232, 200, 111, 65, 173, 203, 11, 53, 202, 108, 245, 18, 206, 54, 137, 36, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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: