Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0317acb3710c19b9c1454c8a58f436e8455e5814ad7e70faeae67a9d3f1f352

Tx prefix hash: e5e2d760fe57f59283b189f6156dd738eda63c025a3bafc2649d2bba76ed3fda
Tx public key: f13348c5d930d9fd01c38d0fb4f33dce1ec179f95f7aaf2863a11ab4ba7bfddf
Timestamp: 1738874012 Timestamp [UTC]: 2025-02-06 20:33:32 Age [y:d:h:m:s]: 01:141:06:44:52
Block: 1213607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353297 RingCT/type: yes/0
Extra: 01f13348c5d930d9fd01c38d0fb4f33dce1ec179f95f7aaf2863a11ab4ba7bfddf021100000018007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa8755bd3668a2f8b5036844b71e5b5abcbcc081a973f056b95bef35242363af 0.000600000000 1700386 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": 1213617, "vin": [ { "gen": { "height": 1213607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa8755bd3668a2f8b5036844b71e5b5abcbcc081a973f056b95bef35242363af" } } ], "extra": [ 1, 241, 51, 72, 197, 217, 48, 217, 253, 1, 195, 141, 15, 180, 243, 61, 206, 30, 193, 121, 249, 95, 122, 175, 40, 99, 161, 26, 180, 186, 123, 253, 223, 2, 17, 0, 0, 0, 24, 0, 127, 151, 138, 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: