Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356f1d1c0f67f452cdd0ef2ff7e949ac711582dcd7d26a66ef64eae6e1e7ecf6

Tx prefix hash: 305725265297eadf83bc88f1363f4fbdf71015baf9a71af78b66702dac8517c9
Tx public key: ec49e91d331355e0f93a2c68672000d41945034f9f34a1e4061ecf6eb3d60542
Timestamp: 1739412659 Timestamp [UTC]: 2025-02-13 02:10:59 Age [y:d:h:m:s]: 01:016:08:55:23
Block: 1218063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270241 RingCT/type: yes/0
Extra: 01ec49e91d331355e0f93a2c68672000d41945034f9f34a1e4061ecf6eb3d60542021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 623d65732c0a726eb6b580287388d4fae05bc35c09d991cd87c95cfabdc8b915 0.000600000000 1704878 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": 1218073, "vin": [ { "gen": { "height": 1218063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "623d65732c0a726eb6b580287388d4fae05bc35c09d991cd87c95cfabdc8b915" } } ], "extra": [ 1, 236, 73, 233, 29, 51, 19, 85, 224, 249, 58, 44, 104, 103, 32, 0, 212, 25, 69, 3, 79, 159, 52, 161, 228, 6, 30, 207, 110, 179, 214, 5, 66, 2, 17, 0, 0, 0, 1, 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) | dinastycoin version: tesla-369