Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ce8dfeeb50ab76537bed2e4c5ff4e3d60b41d85ce9df1201abea34a853e5683

Tx prefix hash: ed4f13e77850109c97fee1e813d4c8b4f67f56139ffd449282f263e7988701a8
Tx public key: b7c937f8e5a0536138c6ce0ebbde284b4c058b489a7b88b78efb1505c671acd4
Timestamp: 1744586594 Timestamp [UTC]: 2025-04-13 23:23:14 Age [y:d:h:m:s]: 01:220:20:36:28
Block: 1260904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422004 RingCT/type: yes/0
Extra: 01b7c937f8e5a0536138c6ce0ebbde284b4c058b489a7b88b78efb1505c671acd40211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1a26984d73fc0040a661c1d174adb5eb7fc239d314d2bfb707124ee313a0c49b 0.000600000000 1748069 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": 1260914, "vin": [ { "gen": { "height": 1260904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a26984d73fc0040a661c1d174adb5eb7fc239d314d2bfb707124ee313a0c49b" } } ], "extra": [ 1, 183, 201, 55, 248, 229, 160, 83, 97, 56, 198, 206, 14, 187, 222, 40, 75, 76, 5, 139, 72, 154, 123, 136, 183, 142, 251, 21, 5, 198, 113, 172, 212, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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: