Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a6ffeb70d2c783acf2e7bb07ae0f7a1443749846c4fa9bd38b3959c34c8015

Tx prefix hash: 4f3657cffaa211a63ed00ad12d56b9f9484bf23fba5f2925be12f23e73e5e6b5
Tx public key: b33e62a9883ebb44f021c7e5fc2ced546e5f7ce28d5801fa63077cbd27c6407d
Timestamp: 1758773706 Timestamp [UTC]: 2025-09-25 04:15:06 Age [y:d:h:m:s]: 01:051:09:35:16
Block: 1375887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303055 RingCT/type: yes/0
Extra: 01b33e62a9883ebb44f021c7e5fc2ced546e5f7ce28d5801fa63077cbd27c6407d021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: afff4ebc9d3e1c6e38a1c2b6f530c7b4f0be248d35fb341fba08d4a4b3be85eb 0.000600000000 1863978 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": 1375897, "vin": [ { "gen": { "height": 1375887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afff4ebc9d3e1c6e38a1c2b6f530c7b4f0be248d35fb341fba08d4a4b3be85eb" } } ], "extra": [ 1, 179, 62, 98, 169, 136, 62, 187, 68, 240, 33, 199, 229, 252, 44, 237, 84, 110, 95, 124, 226, 141, 88, 1, 250, 99, 7, 124, 189, 39, 198, 64, 125, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: