Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118cf83b2efbfff3d14edbf92bbed65e5d751aefdc8148500e8589f79c801cfc

Tx prefix hash: 879070a2e7c727273072f1c9f472c9fa33c1d661f80674ee9a337168a5da2138
Tx public key: 67f8c91c46013f444f0578a8c19667074016e99e88d6a8b1cc2841fff9921b3c
Timestamp: 1755439710 Timestamp [UTC]: 2025-08-17 14:08:30 Age [y:d:h:m:s]: 01:094:09:04:01
Block: 1348553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333675 RingCT/type: yes/0
Extra: 0167f8c91c46013f444f0578a8c19667074016e99e88d6a8b1cc2841fff9921b3c021100000003a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a950ccb38b36ef2eb632647c140380d08ee0e5eb356ef3e7fe00f0e016d752f 0.000600000000 1836480 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": 1348563, "vin": [ { "gen": { "height": 1348553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a950ccb38b36ef2eb632647c140380d08ee0e5eb356ef3e7fe00f0e016d752f" } } ], "extra": [ 1, 103, 248, 201, 28, 70, 1, 63, 68, 79, 5, 120, 168, 193, 150, 103, 7, 64, 22, 233, 158, 136, 214, 168, 177, 204, 40, 65, 255, 249, 146, 27, 60, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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: