Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18cb5556b67b8fe56357e23ccf5747e66e704ca47d60f0e8df8e5ca649a5d498

Tx prefix hash: d274d48104d4e2dd36f39074edf4d99a8bac248f78d92510648c5da64cfc8446
Tx public key: ace4a439fdc5f89c9358e2407b80fc01943f37bfbd70f1286283a68c2a11d62b
Timestamp: 1725127173 Timestamp [UTC]: 2024-08-31 17:59:33 Age [y:d:h:m:s]: 02:081:02:28:35
Block: 1100055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582864 RingCT/type: yes/0
Extra: 01ace4a439fdc5f89c9358e2407b80fc01943f37bfbd70f1286283a68c2a11d62b02110000000be914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d82a2367a5479c1f18f7d2faaccc265fa8eb540e13e900086da1aea50c38eda 0.000600000000 1576028 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": 1100065, "vin": [ { "gen": { "height": 1100055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d82a2367a5479c1f18f7d2faaccc265fa8eb540e13e900086da1aea50c38eda" } } ], "extra": [ 1, 172, 228, 164, 57, 253, 197, 248, 156, 147, 88, 226, 64, 123, 128, 252, 1, 148, 63, 55, 191, 189, 112, 241, 40, 98, 131, 166, 140, 42, 17, 214, 43, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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: